Debris management system and method of operation thereof

ABSTRACT

A debris management system for use in space and a method of controlling space debris is disclosed. In one embodiment, the system includes: (1) a frame, (2) a plurality of material sections, coupled to the frame, that cooperate to form a material structure when deployed from the frame and (3) a plurality of microvehicles, coupled to the plurality of material sections, each one of the plurality including propulsion units configured to eject the each one relative to the frame and pull the plurality of material sections to deploy the plurality of material sections to form the material structure.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.13/928,592, entitled “DEBRIS REMOVAL MANAGEMENT SYSTEM AND METHOD OFOPERATION THEREOF,” filed by Daniel W. Allen, et al., on Jun. 27, 2013,which is currently pending and is a continuation of U.S. applicationSer. No. 12/970,319, entitled “DEBRIS REMOVAL MANAGEMENT SYSTEM ANDMETHOD OF OPERATION THEREOF,” filed by Daniel W. Allen, et al., on Dec.16, 2010, which is currently pending and claims the benefit of U.S.Provisional Application Ser. No. 61/287,059, filed by Allen, et al., onDec. 16, 2009, entitled “Debris Removal Management System,” wherein theabove applications are commonly assigned with this application andincorporated herein by reference in their entirety.

TECHNICAL FIELD

This application is directed, in general, to satellites and, morespecifically, to satellites capable of at least intercepting spacedebris.

BACKGROUND

Space debris (also known as “orbital debris,” “space junk” or “spacewaste”) presents a serious collision risk for launch vehicles, orbitalvehicles and satellites. Space debris can range in size from spent solidrocket motor cases to nuts, bolts and tiny bits of old launch vehiclesto entire spent rocket stages and defunct satellites. However, the sizeof the debris is essentially irrelevant, since typical collision speedsare on the order of a few to tens of kilometers per second. At thosespeeds, even tiny debris can punch into functioning vehicles andsatellites, sometimes breaching their skin, crippling their electronicsand compromising their missions.

The problem of space debris has only become worse over the decades.While the orbits of space debris do eventually decay, and old spacedebris reenters the Earth's atmosphere and is destroyed, far more debrisis added each year through new vehicle launches and satellite failuresthan is removed through reentry.

The conventional response to the problem of space debris has consistedof avoiding the creation of further space debris, using sacrificiallayers of protection (e.g., foil) to protect sensitive equipment,altogether steering clear of known space debris and relying on orbitaldecay to remove space debris. Unfortunately, foil and extra fuel addweight and complexity to space structures and do not guaranteeprotection, especially from larger debris; much of the smaller spacedebris is undetectable and so cannot be avoided; and orbital decay takesan unreasonable amount of time (sometimes decades) to happen.Consequently, space debris remains a serious threat to further spaceexploration and exploitation.

SUMMARY

One aspect provides a debris management system for use in space. In oneembodiment, the system includes: (1) a frame, (2) a plurality ofmaterial sections, coupled to the frame, that cooperate to form amaterial structure when deployed from the frame and (3) a plurality ofmicrovehicles, coupled to the plurality of material sections, each oneof the plurality including propulsion units configured to eject the eachone relative to the frame and pull the plurality of material sections todeploy the plurality of material sections to form the materialstructure.

In another aspect, a method of controlling space debris is disclosed. Inone embodiment, the method includes: (1) causing a plurality ofmicrovehicles to be ejected relative to a frame of a debris managementsystem employing propulsion units of the microvehicles, the plurality ofmicrovehicles being tethered to a plurality of material sections, (2)consequently causing the plurality of material sections to be deployed,the plurality of material sections cooperating to form a materialstructure, (3) intercepting the space debris employing the materialstructure and (4) controlling movement of the space debris employing theplurality of microvehicles and the material structure.

In another aspect, another embodiment of a debris management system forspace is disclosed. In this other embodiment, the debris managementsystem includes: (1) a frame including a base, (2) a plurality ofmaterial sections coupled to the frame, (3) a plurality ofmicrovehicles, coupled to the plurality of material sections, havingpropulsion units, a reaction control system and an electrical powersystem, the plurality of microvehicles configured to employ thepropulsion units to be ejected relative to the frame and deploy theplurality of material sections by pulling an outer edge of the pluralityof material sections away from the frame, the plurality of materialsections cooperating to form a material structure and (4) an enclosurefairing hingedly coupled to the base.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunctionwith the accompanying drawings, in which:

FIG. 1 is an elevational view of a launch vehicle that may be employedto transport various embodiments of a DRMS;

FIG. 2 is a cutaway view of a portion of a payload fairing of FIG. 1containing, in particular, a launch vehicle adapter that, in turn,supports and ultimately dispenses, a stack of two DRMSs;

FIG. 3 is an elevational view of the launch vehicle adapter and stack oftwo DRMSs of FIG. 2 showing in greater detail a dual payload adapterassociated with the launch vehicle adapter;

FIG. 4 is an elevational view of one of the stack of two DRMSs of FIG. 3following a release of one of the stack of two DRMSs and showing arelease of the dual payload adapter;

FIG. 5 is an isometric view of one embodiment of a DRMS constructedaccording to the principles of the invention showing the DRMS in a fullyclosed state;

FIG. 6 is an isometric view of the DRMS of FIG. 5 showing the DRMS in apartially open state;

FIG. 7 is an isometric view of the DRMS of FIG. 5 showing the DRMS in afully open state;

FIG. 8 is a plan view of the DRMS of FIG. 7 shown in the fully openstate;

FIG. 9 is an elevational view of the DRMS of FIG. 7 shown in the fullyopen state;

FIG. 10 is a portion of the isometric view of FIG. 7 showing inparticular microvehicles located in respective microvehicle housings andconfigured to employ sections of a net;

FIG. 11 is a portion of the isometric view of FIG. 7 showing doors ofthe microvehicle housings of FIG. 10 in an open state;

FIG. 12 is a portion of the isometric view of FIG. 7 showing themicrovehicles ejecting from their respective microvehicle housings todeploy corresponding net sections;

FIG. 13 is a further isometric view of a portion of the DRMS of FIG. 5showing the microvehicles ejecting from their respective microvehiclehousings to deploy corresponding net sections;

FIG. 14 is yet a further isometric view of a portion of the DRMS of FIG.13 showing the microvehicles ejecting from their respective microvehiclehousings to deploy corresponding net sections;

FIG. 15 is a plan view of one of the microvehicles of FIGS. 13 and 14deploying a corresponding section of the net;

FIG. 16 is an isometric view of the DRMS of FIG. 5 showing the netthereof in a fully deployed state;

FIG. 17 is an elevational view of the DRMS of FIG. 5 showing the netthereof in the fully deployed state;

FIG. 18 is a portion of the elevational view of the DRMS of FIG. 5showing the net thereof in the fully deployed state;

FIG. 19 is an isometric view of the DRMS of FIG. 18 approaching anexample of a piece of space debris, namely a spent upper stage of alaunch vehicle;

FIG. 20 is an isometric view of the DRMS of FIG. 18 coming into contactwith the piece of space debris; and

FIG. 21 is a flow diagram of one embodiment of a method of operating aDRMS carried out according to the principles of the invention.

DETAILED DESCRIPTION

As stated above, space debris remains a serious threat to further spaceexploration and exploitation. Introduced herein are various embodimentsof a DRMS configured to encounter space debris. Some embodiments of theDRMS are configured further to collect and move the space debris toanother location that is regarded as being safe. That location may be ina new but safer orbit, or the DRMS may reenter with such collecteddebris as mission objectives may determine.

Mission and mission objectives often depend on object size and thevelocity of the debris relative to that of the DRMS (“delta velocity”).One mission involves small debris having a high delta velocity (e.g., inexcess of 7 km/sec). In such mission, the objective is not to try tocollect the debris, but instead to slow the debris' velocity such thatits orbit is degraded at an accelerated rate, and the risk of collisionis reduced. Another mission involves small debris having a low deltavelocity (e.g., less than 2 km/sec) and small and large debris havingvery low delta velocities (e.g., less than 10 m/sec). In such mission,the objective is to capture the debris and perhaps remove it to anotherlocation (including causing the DRMS to reenter with it. Yet anothermission involves a single piece of very large debris (e.g., a defunctsatellite or an expended launch vehicle) having a very low deltavelocity. In such mission, the objective is to capture the debris andperhaps remove it. However, the objective may involve adapting thestructure of the DRMS to the size and configuration of the debris, allthe better to capture it reliably.

Various embodiments of the DRMS have various standardized launch vehicleinterfaces, allowing the DRMS to be launched on different rocket launchvehicle types and sizes, as well as allowing the DRMS to be launched asan auxiliary payload (“rideshare”). Another embodiment of the DRMS maybe launched solo as a primary launch payload or launched as a ridesharewith other payloads on a launch of opportunity. In other embodiments,multiple DRMSs are located on a support or host satellite and configuredto be deployed on demand as the host satellite is in orbit.

FIG. 1 is an elevational view of a launch vehicle 100 that may beemployed to transport various embodiments of a DRMS. The launch vehicle100 has a payload fairing (PLF) 110 within which various payloads may becarried into space. In the illustrated embodiment, the launch vehicle100 carries at least one DRMS (not shown) within its PLF 110. Thespecific launch vehicle 100 illustrated in FIG. 1 is a Falcon 1e, whichis commercially available from Space Exploration TechnologiesCorporation of Hawthorne, Calif. However, those skilled in the pertinentart should understand that any conventional or later-developed launchvehicle capable of carrying the DRMS into space may be employed in lieuof a Falcon 1e.

FIG. 2 is a cutaway view of a portion of the PLF 110 of FIG. 1containing, in particular, a launch vehicle adapter 210 that, in turn,supports and ultimately dispenses, a stack of two DRMSs 220, 230. FIG. 2shows the DRMSs 220, 230 as they may be configured during launch andinitial flight of the launch vehicle 100.

In the embodiment of FIG. 2, the DRMS 220 (a “first DRMS”) and the DRMS230 (a “second DRMS”) are stacked in a generally vertical arrangement. Adual payload adapter 240 is associated with the launch vehicle adapter210 and configured to allow the launch vehicle adapter 210 to supportthe first DRMS 220 directly and without having to employ the second DRMS230 to support the first DRMS 220. In the illustrated embodiment, thedual payload adapter 240 is generally cylindrical and surrounds thesecond DRMS 230. As will be illustrated below, the dual payload adapter240 is configured to be used only to effect release of the first DRMS220. Alternative embodiments of the dual payload adapter 240 may beemployed in other phases of a mission. Alternative embodiments of thelaunch vehicle adapter 210 are configured to support more than twoDRMSs, some in stacked configurations, some in tandem configurations.

In the illustrated and other, alternative embodiments, a “mother ship”(not shown) is configured to support multiple DRMSs. Various embodimentsof such mother ship have a larger propulsion bus, an RCS, an EPS, a databus system and various systems needed to navigate through space. As withthe launch vehicle adapter 210 described above, one embodiment of themother ship is attached to the launch vehicle with a suitablebus-to-launch vehicle interstage adapter interface. In variousembodiments, the mother ship has one or more of navigation equipment,data links, EPS, Command, Control and Telemetry (CC&T) and antennas forsatellite/ground communications and other equipment. In thisconfiguration, DRMSs could remain dormant until mission requirementsdictate deployment and execution of debris management.

FIG. 3 is an elevational view of the launch vehicle adapter and stack oftwo DRMSs 220, 230 of FIG. 2 showing in greater detail the dual payloadadapter 240 associated with the launch vehicle adapter 210. FIG. 3 showsthe DRMSs 220, 230 after the PLF 110 has been ejected but before eitherDRMS 220, 230 has been released.

FIG. 4 is an elevational view of one of the stack of two DRMSs 220, 230of FIGS. 2 and 3 following release of the first DRMS 220 of FIGS. 2 and3) and during release of the dual payload adapter 240. Morespecifically, FIG. 4 shows only the second DRMS 230, and the dualpayload adapter 240 is being jettisoned upwardly as shown. In theillustrated embodiment, the dual payload adapter 240 clears the secondDRMS 230 before the second DRMS 230 is released. In one embodiment, thedual payload adapter 240 is tethered to the launch vehicle adapter 210of FIGS. 2 and 3 to prevent it from becoming another piece of spacedebris. Those skilled in the pertinent art should understand that otherways exist to carry one or more DRMSs on a single launch vehicle andthat the broad scope of the invention is not limited to the particularembodiments illustrated and described.

FIG. 5 is an isometric view of one embodiment of a DRMS 500 constructedaccording to the principles of the invention showing the DRMS 500 in afully closed state.

The DRMS 500 of FIG. 5 has a cap 510, an upper enclosure fairing 520 anda lower enclosure fairing 530. A first set of hinges 540 couples theupper enclosure fairing 520 to the lower enclosure fairing 530. A secondset of hinges 550 couples the lower enclosure fairing 530 to a base 560.In the illustrated embodiment, the upper and lower enclosure fairings520, 530 serve to protect internal portions of the DRMS 500 from damageduring ground processing and while in space and further offer protectionfrom ultraviolet (UV) radiation while orbiting. As will be seen insubsequent FIGS. 6-20, the upper and lower enclosure fairings 520, 530are divided into sections, allowing them to be peeled outward much asthe skin is peeled from a banana. Thus peeled, portions of the DRMS 500that are housed inside the upper and lower enclosure fairings 520, 530are exposed and allowed to function.

As described above, the DRMS 500 is typically deployed in conjunctionwith a main bus, a propulsion bus or a support/host satellite (notshown). The propulsion bus or support/host satellite may be of anysuitable conventional or later-developed type and will not be furtherdescribed in FIG. 6, et seq., because it operates largely independentlyof the DRMS 500. Its general function is to transport the DRMS 500 to adesired location and perhaps thereafter to assist the DRMS 500, alongwith any space debris it may have collected, to another location.

In one embodiment, the DRMS 500 includes a robotic arm (not shown). Inone specific embodiment, the cap 510 supports the robotic arm. Inalternative embodiments, other parts of the DRMS 500 support the roboticarm. The robotic arm, if included in a particular embodiment, isconfigured to grasp other objects, e.g., an errant satellite, a piece ofdebris, a launch vehicle adapter or a launch vehicle.

In one embodiment, the main bus is a commercial off-the-shelf (COTS)propulsion bus having its own propulsion, reaction control system (RCS),electrical power system (EPS) and data bus system. In addition to these,the main bus typically includes a mechanical and electrical interface tothe DRMS 500, allowing it to move the DRMS 500 about and communicate andcoordinate with it. In the illustrated embodiment, the main bus isattached to the DRMS 500 at one end (e.g., the base 560). In a relatedembodiment, the main bus is attached to the launch vehicle with asuitable main bus-to-launch vehicle interstage adapter interface at theother end.

FIG. 6 is an isometric view of the DRMS 500 of FIG. 5 showing the DRMS500 in a partially open state. Shown are the cap 510 and the lowerenclosure fairing 530. The upper enclosure fairing is shown partiallyopen and divided into a plurality of upper enclosure fairing sections620 though larger embodiments may have additional sections 620 and 730.The specific embodiment of FIG. 6 has four such upper enclosure fairingsections 620. The first set of hinges (540 of FIG. 5) allow the fourupper enclosure fairing sections 620 to rotate outwardly relative to thelower enclosure fairing 530 of FIG. 5. Now exposed, various portions ofthe DRMS 500 that were previously occluded become apparent.

FIG. 6 shows a plurality of microvehicle housings 630. The microvehiclehousings 630 are configured to house microvehicles (not shown in FIG. 6,but shown and described in conjunction with subsequent FIGs.) Themicrovehicle housings 630 are shown without doors. In one embodiment,the microvehicle housings 630 lack doors. In the illustrated embodiment,however, the microvehicle housings 630 have doors. However, FIGS. 6-10omit the doors for clarity's sake. FIGS. 11-14, described below, showone embodiment of the doors.

FIG. 6 also shows a corresponding plurality of net sections 640. In oneembodiment, the plurality of net sections 640 are physically separatefrom one another. In an alternative embodiment, the plurality of netsections 640 are regions of the same net. In the specific embodiment ofFIG. 6, the net sections 640 are stored as a generally cylindrical roll.In alternative embodiments, the net sections 640 are stored as multiplerolls. In further embodiments, the net sections 640 are stored as foldedstacks. A support member 650 extends upwardly through a center of thenet sections 640 as shown to support the plurality of microvehiclehousings 630 and the cap 510. The support member 650, together with thebase 560, form a frame of the DRMS 500.

FIG. 7 is an isometric view of the DRMS 500 of FIG. 5 showing the DRMSin a fully open state. Both the upper and lower enclosure fairings ofFIG. 5 are shown in their fully open state. As with the upper enclosurefairing of FIG. 6, the lower enclosure fairing of FIG. 7 is shown asbeing divided into a plurality of lower enclosure fairing sections 730.The specific embodiment of FIG. 7 has four such lower enclosure fairingsections 730. Just as the first set of hinges 540 of FIG. 5 allowed theupper enclosure fairing sections 620 to rotate outwardly relative to thelower enclosure fairing 530 of FIG. 5, the second set of hinges 550 ofFIG. 5 allow the lower enclosure fairing sections 730 to rotateoutwardly relative to the base 560. FIG. 7 shows a corresponding numberof actuating arms 740 that urge the lower enclosure fairing sections 730outwardly. Although FIG. 7 does not show them, a corresponding number ofsimilar actuating arms are provided and configured to urge the upperenclosure fairing sections 620 to rotate outwardly. Alternativeembodiments employ actuator motors in lieu of, or in addition to, theactuating arms 740 or the actuating arms for the upper enclosure fairingsections 620.

In the illustrated embodiment, the net sections 640 are rolled or foldedto allow large sections of net to be stored and deployed easily. Invarious embodiments, the net sections 640 are made of a material that isselectable in terms of type to meet a specific mission requirement. Inone embodiment, the net sections 640 are made of rip-stop material(e.g., Nylon®, commercially available from the E.I. du Pont de Nemoursand Company of Wilmington, Del.) to provide resistance against rippingthat may otherwise occur when debris penetrates the net. In anotherembodiment, the net sections 640 are made of a puncture-resilientmaterial (e.g., Kevlar®, commercially available from the E.I. du Pont deNemours and Company of Wilmington, Del.). In yet another embodiment, thenet sections 640 are made of a non electromagnetic-radiation penetratingmaterial or any combination of materials.

In various embodiments, the net sections 640 are made of a material thatis selectable in terms of size and shape to meet a specific missionrequirement. In various embodiments, the net sections 640 range in sizefrom large (e.g., hundreds of square meters) to small (e.g., only tensof meters) as mission requirements dictate. In the illustratedembodiment, the net sections 640 are generally triangular, with a focalpoint at the support member 650 with the wide part of the material 640on the outer edge of the deployed material, though the broad scope ofthe invention is not limited to a particular shape or number of shapes.

In various embodiments to be illustrated and described herein, the netsections are attached to the DRMS 500 at inner edges thereof (e.g., tothe support member 650) and to at least one microvehicle at outer edgesthereof. In the embodiment of FIG. 6, the net sections are attached tothe DRMS 500 at inner edges thereof and four microvehicles (onemicrovehicle per section) at outer edges thereof.

FIG. 8 is a plan view of the DRMS 500 of FIG. 7 shown in the fully openstate. FIG. 8 is presented primarily for the purpose of illustrating howthe upper and lower enclosure fairing sections 620, 730, the netsections 640 and the plurality of microvehicle housings 630 may beradially arranged with respect to one another when the DRMS 500 is inits fully open state. The configuration is such that a correspondingplurality of microvehicles (not shown in FIG. 8) can be ejected radiallyoutwardly from the plurality of microvehicle housings (unreferenced inFIG. 8) and how the plurality of microvehicles can deploy the netsections 630 that lie “below” them.

FIG. 9 is an elevational view of the DRMS 500 of FIG. 7 shown in thefully open state. FIG. 9 is presented primarily for the purpose ofillustrating one possible relative configuration among the upper andlower enclosure fairing sections 620, 730, the base 560, the netsections 640 and the plurality of microvehicle housings 630. Theconfiguration is such that the plurality of microvehicle housings 630can deploy the net sections 630 without interference from the upper andlower enclosure fairing sections 620, 730.

FIG. 10 is a portion of the isometric view of FIG. 7 showing inparticular a plurality of microvehicles 1010 located in their respectivemicrovehicle housings 630 and configured to employ sections of a net(not shown in FIG. 10). It should be noted that the net sections 640shown in FIG. 7 are omitted from FIG. 10.

In the illustrated embodiment, each microvehicle includes propulsion,RCS, EPS and data bus systems 1510. The microvehicles 1010 areconfigured to respond to a command from the DRMS 500 to eject and travel(e.g., linearly) to a location distal from the DRMS 500. In doing so,the microvehicles 1010 drag corresponding net sections behind them,deploying them. The microvehicles 1010 may later respond to one or morecommands from the DRMS 500 to return to the DRMS 500 or converge withother microvehicles 1010 to close the net sections (tantamount todrawing the drawstring on a bag) and thereby retain any space debristhat has been captured in the net sections. In the illustratedembodiment, the microvehicles 1010 are commercially available, e.g.,from SpaceQuest, Ltd, of Fairfax, Va. Alternative embodiments employconventional microvehicles that are commercially available from othermanufacturers or later-developed microvehicles.

It should also be noted that FIG. 10, like the FIGs. before it, do notshow the doors on the microvehicle housings 630 for the sake of clarity.One embodiment of such doors will now be illustrated and described. FIG.11 is a portion of the isometric view of FIG. 7 showing doors 1110 ofthe microvehicle housings 630 of FIG. 10 in an open state. Theillustrated embodiment of each door 1110 exists in a single piece,hinged on one side. In the embodiment of FIG. 11, the DRMS 500 isconfigured to command the doors 1110 to open as needed to allow themicrovehicles 1010 to be ejected or protect the microvehicles 1010 fromdamage.

FIG. 12 is a portion of the isometric view of FIG. 7 showing themicrovehicles 1010 ejecting from their respective microvehicle housings630 to deploy corresponding net sections. For clarity's sake, only oneof the microvehicle housings 630 and doors 1110 is referenced in FIG.12.

As is apparent, the microvehicles 1010 have been ejected from theirmicrovehicle housings 630 and are traveling in a generally straight linedirectly radially outwardly from the microvehicle housings 630. In oneembodiment, ejection of the microvehicles 1010 is carried out usingpotential energy stored in a spring located in each of the microvehiclehousings 630. In the illustrated embodiment, ejection of themicrovehicles 1010 is carried out using the propulsion systems in themicrovehicles 1010. As is also apparent, each of the microvehicles 1010is tethered to a leading edge portion (unreferenced) of a correspondingnet section 640, as evidenced by the leading edge portion unfurling. Atether couples the microvehicles to their respective leading edge. FIG.12 shows, but does not reference, the tethers for clarity's sake.

In various embodiments, the DRMS 500 directly controls the microvehicles1010. In other embodiments, the microvehicles 1010 are semi- or fullyautonomous. In certain embodiments, the microvehicles 1010 are scalablein terms of size and/or number per net section depending on the size ofeach net section to be deployed.

FIGS. 13-15 show various phases in net section deployment. FIG. 13 is afurther isometric view of a portion of the DRMS of FIG. 5 showing themicrovehicles 1010 ejecting from their respective microvehicle housingsto deploy corresponding net sections. FIG. 13 is presented primarily forthe purpose of illustrating tethers 1310 that couple the microvehicles1010 to leading edges of corresponding net sections 640. FIG. 14 is yeta further isometric view of a portion of the DRMS of FIG. 13 showing themicrovehicles ejecting from their respective microvehicle housings todeploy corresponding net sections 640. FIG. 15 is a plan view of one ofthe microvehicles 1010 of FIGS. 13 and 14 deploying a corresponding netsection 640.

FIG. 16 is an isometric view of the DRMS of FIG. 5 showing the netthereof in a fully deployed state. FIG. 16 demonstrates that, at leastin the illustrated embodiment, the overall size of the net sections 640dwarfs the DRMS 500. The result is that a relatively large space debriscollection area is presented for use.

FIG. 17 is an elevational view of the DRMS of FIG. 5 showing the netthereof in the fully deployed state. FIG. 17 is presented primarily forthe purpose of showing the relationship of the net sections 640 to theDRMS 500.

FIG. 18 is a portion of the elevational view of the DRMS of FIG. 5showing the net thereof in the fully deployed state. FIG. 18 ispresented primarily for the purpose of showing that the deployed netsections 640 clear the upper and lower enclosure fairing sections 620,730.

FIG. 19 is an isometric view of the DRMS of FIG. 18 approaching anexample of a piece of space debris, namely a spent upper stage 1910 of alaunch vehicle. In fact, FIG. 19 shows a Centaur, which has a nominaldiameter of about 10 ft. This relatively large diameter is still smallwhen compared to the size of the net sections of the DRMS 500. FIG. 20is an isometric view of the DRMS 500 of FIG. 18 coming into contact withthe spent upper stage 1910. At or near contact with the spent upperstage 1910, the DRMS 500 commands the microvehicles to close the netsections, perhaps by converging with each other to close the netsections and thereby retain the spent upper stage 1910. In oneembodiment, the DRMS 500 then moves to a safer location. In a morespecific embodiment, the DRMS 500 de-orbits and reenters the atmosphereto destroy itself and the spent upper stage 1910.

FIG. 21 is a flow diagram of one embodiment of a method of operating aDRMS carried out according to the principles of the invention. Themethod begins in a start step 2110. In a step 2120, a plurality of upperenclosure fairing sections are opened. In a step 2130, a plurality oflower enclosure fairing sections are opened. In a step 2140, a pluralityof microvehicles are caused to be ejected relative to a frame of a DRMS,perhaps from a corresponding plurality of microvehicle housings. In oneembodiment, the microvehicles are deployed using propulsion units in themicrovehicles. The plurality of microvehicles are tethered to acorresponding plurality of net sections. In a step 2150, thecorresponding plurality of net sections are consequently caused to bedeployed, perhaps from a generally cylindrical roll. The plurality ofnet sections cooperate to form a net configured to capture space debris.In a step 2160, the space debris is intercepted. In a step 2170, theplurality of microvehicles are commanded to close the net sections. TheDRMS can then move to a safer location, perhaps de-orbiting andreentering the atmosphere to destroy itself and the space debris. Themethod ends in an end step 2180.

Those skilled in the art to which this application relates willappreciate that other and further additions, deletions, substitutionsand modifications may be made to the described embodiments.

What is claimed is:
 1. A debris management system for use in space,comprising: a frame; a plurality of material sections, coupled to saidframe, that cooperate to form a material structure when deployed fromsaid frame; and a plurality of microvehicles, coupled to said pluralityof material sections, each one of said plurality including propulsionunits configured to eject said each one relative to said frame and pullsaid plurality of material sections to deploy said plurality of materialsections to form said material structure.
 2. The system as recited inclaim 1 wherein each of said plurality of material sections isconstructed of a same material that is a non electromagnetic-radiationpenetrating material.
 3. The system as recited in claim 1 wherein eachof said plurality of material sections have a triangular shape with afocal point coupled to said frame when said plurality of materialsections are deployed to form said material structure.
 4. The system asrecited in claim 3 wherein each of said plurality of material sectionshave a wide part opposite said focal point when said plurality ofmaterial sections are deployed and at least one of said plurality ofmicrovehicles is coupled to said wide part of said plurality of materialsections.
 5. The system as recited in claim 1 wherein said plurality ofmicrovehicles are configured to employ said propulsion units to movesaid material structure.
 6. The system as recited in claim 1 whereinsaid each one of said plurality of microvehicles further includes areaction control system, an electrical power system and data bussystems.
 7. The system as recited in claim 1 wherein said debrismanagement system commands said plurality of microvehicles to be ejectedrelative to said frame.
 8. A method of controlling space debris,comprising: causing a plurality of microvehicles to be ejected relativeto a frame of a debris management system employing propulsion units ofsaid microvehicles, said plurality of microvehicles being tethered to aplurality of material sections; consequently causing said plurality ofmaterial sections to be deployed, said plurality of material sectionscooperating to form a material structure; intercepting said space debrisemploying said material structure; and controlling movement of saidspace debris employing said plurality of microvehicles and said materialstructure.
 9. The method as recited in claim 8 wherein said controllingincludes employing said propulsion units of said plurality ofmicrovehicles to move said material structure.
 10. The method as recitedin claim 8 wherein said controlling includes collecting and moving saidspace debris.
 11. The method as recited in claim 8 wherein saidintercepting includes placing said material structure in a path of saidspace debris.
 12. The method as recited in claim 8 wherein saidcontrolling includes causing at least one of said plurality ofmicrovehicles to at least partially close said plurality of materialsections.
 13. The method as recited in claim 12 wherein said each one ofsaid plurality of microvehicles includes a reaction control system andsaid employing said plurality of microvehicles includes employing saidreaction control system.
 14. The method as recited in claim 8 whereinsaid plurality of microvehicles are coupled to an outer edge of saidplurality of material sections and said frame is coupled to an inneredge of said plurality of material sections.
 15. A debris managementsystem for space, comprising: a frame including a base; a plurality ofmaterial sections coupled to said frame; a plurality of microvehicles,coupled to said plurality of material sections, having propulsion units,a reaction control system and an electrical power system, said pluralityof microvehicles configured to employ said propulsion units to beejected relative to said frame and deploy said plurality of materialsections by pulling an outer edge of said plurality of material sectionsaway from said frame, said plurality of material sections cooperating toform a material structure; and an enclosure fairing hingedly coupled tosaid base.
 16. The system as recited in claim 15 wherein each one ofsaid plurality of microvehicles includes communication circuitry. 17.The system as recited in claim 15 wherein said enclosure fairing is alower enclosure fairing and said system further includes an upperenclosure fairing hingedly coupled to said lower enclosure fairing. 18.The system as recited in claim 15 wherein each of said plurality ofmaterial sections is constructed of a non electromagnetic-radiationpenetrating material.
 19. The system as recited in claim 15 wherein eachof said plurality of material sections is constructed of apuncture-resilient material.
 20. The system as recited in claim 15wherein each of said plurality of material sections include an inneredge that is coupled proximate to said frame.